✅ ### Completed Work
Technical Choices:

• Established a new creedentgo Angular Plugin
• Established a new GitHub repository
• Set up a test Angular project to validate plugin behavior.

Arguments & Research:

• Don't mix specific framework rules to generic TS/JS rules of credengo-javascript
• TypeScript standard AST doesn't capture specific Angular syntax
• Validated the relevance of Creedengo Angular rules in Angular application.

🚧 Rule Definitions:

• Proposed specific Angular-oriented ecodesign rules.
• Prepared documentation for implementation and evaluation.

🚧Chantiers Progress:

• We have started the migration of ESLint Credengo-js plugin to TypeScript.
• Analyzed how the plugin behaves with an Angular codebase.
• Started writing Angular-specific rules based on real-world patterns.

🕙 Remaining Work

• Plugin Development:
• Finalize and test Angular-specific rules.
• Ensure backward compatibility and integration with ESLint workflows.
• Make sure the new ESLint Angular plugin is properly migrated and properly integrated into SonarQube
• Manage to run an analysis using a Quality Profile integrating our Angular specific rules onto the Angular test project

Quality Assurance:

• Improve project documentation and rule clarity.
• Perform code reviews and align with Creedengo's quality standards.
• Finalization for PR:
• Package the Angular Creedengo plugin.
• Add usage guidelines to the GitHub repository.
• Submit the plugin as a new contribution to the Creedengo ecosystem.